Skip to content

Conversation

Veera-mulge
Copy link
Contributor

@Veera-mulge Veera-mulge commented Oct 15, 2025

What does this PR do?

(Provide a description of what this PR does.)

Test Plan

(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)

Related PRs and Issues

(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)

Have you read the Contributing Guidelines on issues?

(Write your answer here.)

Summary by CodeRabbit

  • Documentation
    • Published a new blog post: “7 Reasons to Migrate from Vercel to Appwrite Sites,” covering workflow parity, full Next.js support, global CDN, cost scalability, broader cloud integration, open source/self-hosting, and a low-disruption migration path.
    • Includes cover image, author, date, estimated reading time, category, featured placement, and a call-to-action.
    • Added concluding section with linked resources for further reading.

Added a blog post detailing seven reasons to migrate from Vercel to Appwrite Sites, highlighting benefits such as improved developer experience, cost efficiency, and full cloud platform integration.
Copy link
Contributor

coderabbitai bot commented Oct 15, 2025

Walkthrough

Adds a new static blog post page at src/routes/blog/post/migrate-from-vercel-to-appwrite-sites/+page.markdoc. The file includes front matter fields (layout, title, description, date, cover, timeToRead, author, category, featured, callToAction) and full markdown content outlining seven reasons to migrate from Vercel to Appwrite Sites: git push workflow parity, full Next.js support, global CDN via multi-CDN, scalable cost structure, broader cloud platform integration, open-source/self-hosting, and a low-disruption migration path. Includes a wrap-up and linked resources. No changes to exported/public entities.

Suggested reviewers

  • tessamero
  • ebenezerdon

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Title Check ⚠️ Warning The title "Migrate from vercel to sites blog" is awkwardly phrased, lacks proper capitalization and the term "Appwrite", and does not clearly convey that a new blog post on migrating from Vercel to Appwrite Sites is being added. Rename the title to clearly reflect the main change with proper capitalization and context, for example "Add blog post on migrating from Vercel to Appwrite Sites".
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch migrate-from-vercel-to-sites-blog

Warning

Review ran into problems

🔥 Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review. If the issue persists, set path_filters to include or exclude specific files.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
src/routes/blog/post/migrate-from-vercel-to-appwrite-sites/+page.markdoc (1)

67-70: Standardize internal link format.

Line 70 uses an absolute URL (https://appwrite.io/...) while the other resource links (lines 68-69) use relative paths. For consistency and to avoid potential routing issues, all internal links should use the same format.

Apply this diff to standardize the link format:

 # More resources
 - [Appwrite Sites documentation](/products/sites)
 - [Announcing Appwrite Sites: The open source Vercel alternative](/blog/post/announcing-appwrite-sites)
-- [Appwrite Sites vs Vercel: Choosing the right web hosting platform](https://appwrite.io/blog/post/open-source-vercel-alternative)
+- [Appwrite Sites vs Vercel: Choosing the right web hosting platform](/blog/post/open-source-vercel-alternative)
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 98d11fb and 182a5be.

📒 Files selected for processing (1)
  • src/routes/blog/post/migrate-from-vercel-to-appwrite-sites/+page.markdoc (1 hunks)
🔇 Additional comments (2)
src/routes/blog/post/migrate-from-vercel-to-appwrite-sites/+page.markdoc (2)

1-70: LGTM! Well-structured blog post.

The blog post is well-written with clear structure, compelling arguments, and appropriate marketing tone. The content effectively communicates the benefits of migrating from Vercel to Appwrite Sites. The front matter is properly formatted, and the markdown content is well-organized with logical flow from introduction through seven key reasons to the conclusion.


19-19: Verify documentation links and feature claims.

The blog post references several Appwrite features and documentation pages:

  • Line 19: /docs/products/sites/deployments and /docs/products/sites/previews
  • Line 31: /docs/products/network/cdn
  • Lines 45-46: /docs/products/functions, /docs/products/databases, /docs/products/auth
  • Line 53: /docs/advanced/self-hosting
  • Line 57: /docs/products/sites/migrations/vercel

Please ensure these documentation pages exist and the feature descriptions are accurate.

Run the following script to verify the documentation links:

Also applies to: 31-31, 45-46, 53-53, 57-57

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant